op-node: Fix stop sequencer deadlock in op-conductor deployments #13806
+11
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix deadlock introduced by PR #11769 in
*Sequencer.Stopmethod.PR #11769 added a safety mechanism in
*Sequencer.Stopto wait for latestHead to match latestSealed before stopping, preventing single-block reorgs. However, this introduced a deadlock when a sequencer lost leadership during the stop process:latestSealednever updatesThe deadlock prevented proper sequencer shutdown, which could lead to multiple sequencers actively producing blocks.
This PR adds leadership checks during the stop process. If the sequencer is no longer the leader or cannot determine leadership status, it will skip waiting for head synchronization and proceed with the shutdown.